Ask Your Developer: How to Harness the Power of Software Developers and Win in the 21st Century
- Downloads：3507
- Type：Epub+TxT+PDF+Mobi
- Create Date：2021-04-13 09:32:12
- Update Date：2025-09-07
- Status：finish
- Author：Jeff Lawson
- ISBN：B083XL677V
- Environment：PC/Android/iPhone/iPad/Kindle
Reviews
Sebastian Gebski
，
It's a good （or even a very good） book if you meet certain criteria:* you're an executive/decisive person in a typical enterprise that runs in a traditional model and gets beaten by disruptors or more "digital" competitors* you're a business person who'd like to understand why everyone claims that every company is a tech company now （and what does software engineering has in common with that）* you'd like to learn （but for real） what people originally had on their mind when using the phrase "digi It's a good （or even a very good） book if you meet certain criteria:* you're an executive/decisive person in a typical enterprise that runs in a traditional model and gets beaten by disruptors or more "digital" competitors* you're a business person who'd like to understand why everyone claims that every company is a tech company now （and what does software engineering has in common with that）* you'd like to learn （but for real） what people originally had on their mind when using the phrase "digital revolution" and you're tired of all the weasel consultants trying to sell you their bullshitOn the other hand: it's not a book for tech people or start-up enthusiasts （who already understand how start-ups operate）。 They will not find it very revealing （but they will ofc agree with the content）。The book has been written by the CEO of Twilio， but it's not a praise litany for that company。 Obviously， they are there all the time， in the background， but always for an illustratory purpose。 。。。more
Peter O'Kelly
，
Some related resources to consider:t• Book overview: https://www。askyourdeveloper。com/t• Reviews:tt○ https://www。zdnet。com/article/ask-you。。。tt○ https://techcrunch。com/2021/01/15/twi。。。tt○ https://waiyancan。com/summary-ask-you。。。t• Author interview: https://www。forbes。com/sites/tomtaull。。。t• Excerpts/adaptations:tt○ https://www。businessinsider。com/twili。。。tt○ https://hbr。org/2021/01/in-the-digita。。。 Some related resources to consider:t• Book overview: https://www。askyourdeveloper。com/t• Reviews:tt○ https://www。zdnet。com/article/ask-you。。。tt○ https://techcrunch。com/2021/01/15/twi。。。tt○ https://waiyancan。com/summary-ask-you。。。t• Author interview: https://www。forbes。com/sites/tomtaull。。。t• Excerpts/adaptations:tt○ https://www。businessinsider。com/twili。。。tt○ https://hbr。org/2021/01/in-the-digita。。。 。。。more
John Kelleher
，
Easily one of the best business books I’ve read。 Absolutely essential reading for anyone running a business in 2021。
Manouane Beauchamp
，
Livre très intéressant qui nous permet de découvrir l'univers du logiciel。 Jeff Lawson， fondateur et CEO de Twilio， revient sur son expérience personnelle avec ses starts-up， explique le modèle d'affaire de son entreprise actuelle， Twilio， et démontre comment les logiciels peuvent - doivent？ - être considérés comme un moyen central pour offrir des solutions à des individus ou des entreprises。 Plus que tout， il met l'emphase sur l'importance du développeur comme étant la clé de voûte dans l'élabo Livre très intéressant qui nous permet de découvrir l'univers du logiciel。 Jeff Lawson， fondateur et CEO de Twilio， revient sur son expérience personnelle avec ses starts-up， explique le modèle d'affaire de son entreprise actuelle， Twilio， et démontre comment les logiciels peuvent - doivent？ - être considérés comme un moyen central pour offrir des solutions à des individus ou des entreprises。 Plus que tout， il met l'emphase sur l'importance du développeur comme étant la clé de voûte dans l'élaboration de solutions， à une approche en milieu de travail qui met l'emphas sur l'agilité， l'expérimentation et l'apprentissage。 Un livre très inspirant et remplis de constats intelligents construits sur l'expérience concrète de l'auteur。 。。。more
Josh Carlisle
，
Solid read and good adviceGreat read and very insightful。 I especially appreciate the section on the benefits of platform engineering and how to effectively organize teams。
Robert Christie
，
Really nice over from a developer turned CEO on how developers make things happen in the digital world， why it's a good idea to listen to them and involve them - and how to support and enable them。 Really nice over from a developer turned CEO on how developers make things happen in the digital world， why it's a good idea to listen to them and involve them - and how to support and enable them。 。。。more
Yixing J
，
sadly this book is very self-promotional and has a strong marketing purpose， I did not learn anything from it
Richard Bakare
，
This book completely encapsulates the frustrations I have seen over my entire consulting career in trying to demonstrate a vision of how to innovate。 It also details a better roadmap for showing others how to achieve breakthroughs and the tools to do so。 Namely， by creating a culture of experimentation and creativity from the onset。 I am a big believer in the concept of the “Aggregation of Marginal Gains。” A core tenant of this philosophy is tweaking little things to get 1% improvements that com This book completely encapsulates the frustrations I have seen over my entire consulting career in trying to demonstrate a vision of how to innovate。 It also details a better roadmap for showing others how to achieve breakthroughs and the tools to do so。 Namely， by creating a culture of experimentation and creativity from the onset。 I am a big believer in the concept of the “Aggregation of Marginal Gains。” A core tenant of this philosophy is tweaking little things to get 1% improvements that compound when put together。 To identify these one percent improvements， you need to be creative and willing to experiment， a lot。 You also have to be ok with things not working out。 These “failures” should be learning opportunities and not blame sessions。 Those two key principles are what was missing from the conference room in a lot of my customer engagements。 Jeff Lawson does a great job of showing how the old top down， failure is not option， big business approach is getting eaten alive by startups who do the opposite。 Especially， when it comes to giving developers the space to creatively solve problems through experimentation and not requirements documents。 。。。more
João Cortez
，
Excellent book on the human， organizational and management aspects of Software Development by Jeff Lawson - a developer himself and CEO of Twilio。 It touches very good modern practices， it's full of good advice and it contains a lot of statements that will make you think。 Very highly recommended。 Excellent book on the human， organizational and management aspects of Software Development by Jeff Lawson - a developer himself and CEO of Twilio。 It touches very good modern practices， it's full of good advice and it contains a lot of statements that will make you think。 Very highly recommended。 。。。more
Andrus
，
The little there was information about the Twilio way of doing things was really insightful。 For example， the last chapter about devops was a great read/listen to someone not technical like me。 But then there were the numerous pages dedicated to motivate legacy companies to do “digital transformation” （5-10 years late？）， to cover the history of software development， to explain agile development， to promote building on Twilio。 This book tries to cover too much to too many audiences。 I wish there The little there was information about the Twilio way of doing things was really insightful。 For example， the last chapter about devops was a great read/listen to someone not technical like me。 But then there were the numerous pages dedicated to motivate legacy companies to do “digital transformation” （5-10 years late？）， to cover the history of software development， to explain agile development， to promote building on Twilio。 This book tries to cover too much to too many audiences。 I wish there would have been more specifics about 。。 asking the developers。 。。。more
Ric Poh Peng Wang
，
Short and sweet。 I could see more value in my work after getting this book read about platform engineering。
Damir Prusac
，
Well put elements od modern SW DevelopmentA number of good stories and insights how to develop products。 It is written a bit as a twillio marketing promotion material。
Shannon Clark
，
The book to hand to senior execsI don’t know Jeff though full disclosure I do know Eric Ries who wrote the introduction to this book and I do know some of Twillio’s early investors and I’ve been a customer of theirs in the past at previous jobs （and I assume I will use them again at future companies）。 I’ve been online a few years longer than the author and my career has some parallels （multiple startups， stints at larger companies） and while I haven’t （yet） founded a billion dollar corporation m The book to hand to senior execsI don’t know Jeff though full disclosure I do know Eric Ries who wrote the introduction to this book and I do know some of Twillio’s early investors and I’ve been a customer of theirs in the past at previous jobs （and I assume I will use them again at future companies）。 I’ve been online a few years longer than the author and my career has some parallels （multiple startups， stints at larger companies） and while I haven’t （yet） founded a billion dollar corporation my advice to company executives as a part time CTO/COO is nearly identical to much of this book。 In fact I am likely to buy copies of this book for future clients。 So most definitely keep asking your developers - and strive to build organizations and structures to empower them and to connect all parts of your company to customers。 。。。more
Michelle
，
Approachable narrative of the third technical wave of tech with the API economy。 Anyone in this space it is a must read。
Dom
，
The first part of the book provides the annotated / "anecdoted" context of software development history。 I found it crip and informative， yet not overly surprising or new。 I really moved from liking to loving this book once Jeff gets into the nitty-gritty of how to build， nurture and unleash teams and with it digital companies。 It covers much， yet feels right， tight， and supported by many actionable hints， examples and a philosophy that I've been treasuring for a while， and after this book， feel The first part of the book provides the annotated / "anecdoted" context of software development history。 I found it crip and informative， yet not overly surprising or new。 I really moved from liking to loving this book once Jeff gets into the nitty-gritty of how to build， nurture and unleash teams and with it digital companies。 It covers much， yet feels right， tight， and supported by many actionable hints， examples and a philosophy that I've been treasuring for a while， and after this book， feel even better equipped to help nurture， live and build。 Thanks！ Keywording 3 words on a billboard outside San Francisco。 3 out of Features， Deadline， Certainty， and Quality possible at a time， wiggle on Features。 Ask Your Developer = mindset。 Behave compassionately but prioritize ruthlessly。 Benioff the SaaS launching coder。 Beware of coordination complexity。 Bezos' Brain Benders。 Build up the deep bench （e。g。 Amazon's Level 3 GMs） and learn by doing。 Code hairball vs。 microservices。 Commonality: Understanding the problem。 Customer Feel is the ultimate benchmark and multiplier。 Developer rush from direct customer pat: an addiction you wanna nourish。 Differentiation can't be bought， build it。 Digital native vs outsourceable IT cost center。 （Potential） Duplication of efforts crushes perfect synchronization any day。 ESOP for everyone， äh， yup！ Guardrails to set people free。 Hamers hammered it in（g）， UBS he does it again？ Hospitality， not only Service。 Identify with team， not function first。 Instill Importance， Urgency， Focus。 Invest in Infrastructure or be darned by FBATR。 Kanban， Kannst Bannen。 Keep coordination energy negligible， "talk more" ain't the game。 Keep things immediate， small is beautiful。 Learn to build。 Opt-in to complexity。 Permit failure， or fail。 Person that writes the code， wears the pager。 Pink-it！ RAPID without V， otherwise victims。 Platform， the force multiplier。 Safe to be uncertain。 Single-threaded leaders。 Start with the press release。 Tell hero journey to get great talents。 Truth-seekers， not truth-holders。 Write it down or it doesn't count。 。。。more
Jorge DeFlon
，
Una buena narrativa de las prácticas técnicas de desarrollo de software desde el punto de vista ejecutivo。Recomendable para todo gerente de desarrollo o director。
Tom Bayley
，
This is more than a software story。 It's a great insight into creating a culture with a growth mindset and a leadership philosophy that's particular suited on a successful organization which is growing rapidly from its success。 How to maintain the "secret sauce" as you grow and evolve your organization to meet the challenges posed by the future。 Jeff's insights are golden！ This is more than a software story。 It's a great insight into creating a culture with a growth mindset and a leadership philosophy that's particular suited on a successful organization which is growing rapidly from its success。 How to maintain the "secret sauce" as you grow and evolve your organization to meet the challenges posed by the future。 Jeff's insights are golden！ 。。。more
Noe Pion
，
Every big corp depends on software to increase its productivity。 This trend is not new : banks， insurances 。。。 have been using a lot of software for more than 25 years。 Yet， they are getting disrupted by new players on the field， who move extremely fast， and manage to acquire large client bases while keeping headcount small。 So， why couldn't the incumbents do it ？ This book will tell you。Lawson provides a thorough analysis of the organizational structures which make startups so _fast_ and danger Every big corp depends on software to increase its productivity。 This trend is not new : banks， insurances 。。。 have been using a lot of software for more than 25 years。 Yet， they are getting disrupted by new players on the field， who move extremely fast， and manage to acquire large client bases while keeping headcount small。 So， why couldn't the incumbents do it ？ This book will tell you。Lawson provides a thorough analysis of the organizational structures which make startups so _fast_ and dangerous for incumbents。 I imagine this will be useful for managers/execs in legacy corps and consultants。 Among others， he cites :- treating engineers as creatives， instead of Taylorism-like workers checking small-scoped tickets- creating an organization which places clients at its center， for real。- improving iteration speed through reorganization around small teams and microservices- investing in tools for engineers， the same way it is done for HR and Sales- improving tech infrastucture， which acts as a multiplier for tech productivityThere is much more， which is crafted around examples and edge cases， and made me node my head along。He also has few interesting points for people already in "fast" tech， which may be missed by non-technical people but have incredible implications。 One of them is around the commoditization of APIs。 The future of software may be about building elementary blocks used to build more complex software : this is the author's business at Twilio for communication， Stipe for payment， and was already predicted by Hamming's The Art of Doing Science and Engineering。 A crucial difference compared to buying custom-made softwares from IBM， Capgemini， 。。。 is that it enables companies to craft ONLY what makes their business special， and much better integrate with the rest of their software。The book is a quick read， necessary for everyone in legacy companies and wanting to start one， heavily recommended for people interested in organizational systems。 。。。more
Akhil Ramolla
，
For non Devs who want to bring change with software， this book is a master class on how to work with software engineers as of today。
Jake Singer
，
First half of the book was Twilio history， and its place within the context of software development history。 Loved this， A+。 Second half was more or less a manifesto on how to run a more efficient and energizing software organization。 I was a big fan of this， but YMMV - this is really geared towards folks who are （1） execs trying to get the most out of their software engineering orgs， or （2） Founders looking for some inspiration on how to run development。 I think Product Managers might get some First half of the book was Twilio history， and its place within the context of software development history。 Loved this， A+。 Second half was more or less a manifesto on how to run a more efficient and energizing software organization。 I was a big fan of this， but YMMV - this is really geared towards folks who are （1） execs trying to get the most out of their software engineering orgs， or （2） Founders looking for some inspiration on how to run development。 I think Product Managers might get some value out of this too， though some of the descriptions of a ‘bad’ software process might hit too close to home for some。 It definitely triggered some of my Amazon PTSD， but was also inspiring as someone embarking on a new startup project。 4/5 depending on your context！ 。。。more
Rishabh Srivastava
，
This was a guide aimed at teaching managers in legacy companies how to work with developers， though also acted as a thought leadership piece to attract customers and developers to Twilio。Had some useful points， but could’ve definitely been a 3-part blog post。- Running experiments and iterating quickly is everything right now。 outsourcing to agencies or hiring consultants to make software won’t do。 It’s slow， expensive， and generally doesn’t get you the results you need。 Outsourcing also signific This was a guide aimed at teaching managers in legacy companies how to work with developers， though also acted as a thought leadership piece to attract customers and developers to Twilio。Had some useful points， but could’ve definitely been a 3-part blog post。- Running experiments and iterating quickly is everything right now。 outsourcing to agencies or hiring consultants to make software won’t do。 It’s slow， expensive， and generally doesn’t get you the results you need。 Outsourcing also significantly reduces your speed of iteration- We’re moving away from solutions to enabling building blocks。 With these， we can empower internal teams to do so much more with their talents。 With solutions， there was little scope for change- For business people to work together with developers， they should share problems and not solutions。 Don’t ask them to grind out the code。 Just communicate the problem。 Then， let create their own specifications and just vet the specifications to make sure they address the problem- Management: Have small teams with single threaded leaders。 Then， have well documented “communication APIs” to foster effective communication across teams 。。。more
Wallis Chan
，
This is the best book I read on tech management。 Whether you are managing a small team of developers or running a startup， you can learn plenty from this book
Kanishk Dutt
，
It’s a great modern way of building software and managing tech teams。 It is very practical advice for any product manager or any manager around how to build great software and get your developers to participate in a way that helps you win。 Great for unlocking potential from your development。 Have practiced a lot of things suggested and can testify to this advice。
Christopher M
，
This book is phenomenal and a must read for anyone who works with software developers or in digital transformation but does not come from a technical/software development background。
Hesam Andalib
，
Very good narrative of personal and professional experiences。 However， I think the author overemphasizes developers role and disregard the benefits that interdisciplinary collaboration brings to the table。 It is understandable because the product that his company sell is for developers as well。 I love the narrative of the work but I cannot consider it a reliable source of entrepreneurship knowledge and experience for its lack of comprehensiveness。
Davin
，
Great read so insightful thoughts
Sam Aparicio
，
If Marc Andreessen pointed in "Sofware Is Eating The World" to a new breed of software disruptors， Jeff Lawson explains in "Ask Your Developer" how the disruption works and what the disrupted can do about it。It identifies customer experience as the primary frame of reference for strategic success and makes the case that "you can't buy differentiation。 You can only build it。"So companies are either going to go on radical digital transformation journeys or die。 For me， the more interesting implica If Marc Andreessen pointed in "Sofware Is Eating The World" to a new breed of software disruptors， Jeff Lawson explains in "Ask Your Developer" how the disruption works and what the disrupted can do about it。It identifies customer experience as the primary frame of reference for strategic success and makes the case that "you can't buy differentiation。 You can only build it。"So companies are either going to go on radical digital transformation journeys or die。 For me， the more interesting implications of Lawson's ideas are for software companies。 Without openly stating it， he's predicting the demise of app vendors， or at least their demotion to commodities。 He's framing a new imperative for anyone that wants to remain king of the enterprise software hill， which is to build the most important APIs and microservices that developers at enterprises will pick to build their customer-facing apps。If this how it will play out in the next decade， there will be wide-ranging implications for how software is marketed， sold， and serviced。 Because the buyer is the developer。One cannot simply dismiss this book as a puff piece or an extended advertorial for a tech company。 There is some of that。 But at its core this book starts to provide a roadmap for those insiders responsible for navigating the broad transformation happening across the enterprise world。 。。。more
Lau PB
，